Methods and systems for processing electronic disbursements

ABSTRACT

A disbursement module (DM) computer device is provided for processing an electronic disbursement. The DM computer device includes a memory device and a processor. The processor is programmed to register a payor with a disbursement service provided by the DM computer device and to receive a disbursement command from the payor. The disbursement command instructs a disbursement to be made to a payee and includes payee contact information, payee verification data, and a disbursement amount. The processor is further programmed to receive a disbursement request message that includes a payee identifier from the payee requesting that the disbursement be made, and to verify the payee by matching the payee identifier to the payee verification data. The processor is further programmed to electronically transfer funds from a bank account associated with the payor to a bank account associated with the payee.

BACKGROUND OF THE DISCLOSURE

This invention relates generally to processing electronic disbursementsand, more particularly, to network-based methods and systems forprocessing electronic disbursements over a payment card network for abusiness entity electronically disbursing funds to a consumer.

In today's business world, there are times when a consumer must make apayment to a merchant or business entity for a purchase of goods orservice, but there are also times when a merchant or business entity isrequired to make a payment to a consumer. Businesses such as insurancecompanies, governmental entities, and other companies may be requiredduring their normal business operations to make a payment to a consumer.

For example, many insurance companies will issue homeowners insurancepolicies to consumers. If such a policyholder having an insurance policyissued by Insurance Company A suffers damage to his or her home as aresult of a fire, then Insurance Company A may be required to pay fundsto the homeowner under that insurance policy. Those funds may includemoney for temporary living expenses that are needed by the homeownerwhile the home is being repaired. It may be important that thesetemporary living expenses funds are paid out quickly to the homeowner sothat the homeowner can quickly arrange for living accommodations forhimself and his family.

In at least some known situations, Insurance Company A would investigatethe claim, submit the claim, process the claim, and issue a paper checkto the homeowner for these living expenses. Issuing a paper check inthis known situation is both expensive and time consuming.

In fact, it is estimated that today 95% of all businesses (e.g.,insurance companies, governmental entities, and other business) makingpayments to consumers are made by checks that are expensive to managethe printing, replacement, and operations costs. In many cases, there isnot a viable alternative solution for making such payments.

Accordingly, a quicker and more efficient process for business to makepayments to consumers is needed. A process and system is needed thatenables businesses to electronically disburse funds to consumers.

BRIEF DESCRIPTION OF THE DISCLOSURE

In one aspect, a disbursement module (DM) computer device is providedfor processing an electronic disbursement. The DM computer deviceincludes a memory device and a processor. The processor is programmed toregister a payor with a disbursement service provided by the DM computerdevice and to receive a disbursement command from the payor. Thedisbursement command instructs a disbursement to be made to a payee andincludes payee contact information, payee verification data, and adisbursement amount. The processor is further programmed to receive adisbursement request message that includes a payee identifier from thepayee requesting that the disbursement be made, and to verify the payeeby matching the payee identifier to the payee verification data. Theprocessor is further programmed to electronically transfer funds from abank account associated with the payor to a bank account associated withthe payee.

In another aspect, a computer-implemented method is provided forprocessing an electronic disbursement by a disbursement module (DM)computer device. The DM computer device includes a memory device and aprocessor. The method includes registering a payor with a disbursementservice provided by the DM computer device and communicating adisbursement command from the payor to the disbursement serviceinstructing a disbursement to be made to a payee. The disbursementcommand includes payee contact information, payee verification data, anda disbursement amount to be paid to the payee. The method furtherincludes receiving a disbursement request message that includes a payeeidentifier from the payee requesting that the disbursement be made tothe payee. The method further includes matching the payee identifier tothe payee verification data to verify the payee, and electronicallytransferring funds from a bank account associated with the payor to abank account associated with the payee or a payment card for use by thepayee.

In another aspect, one or more non-transitory computer-readable storagemedia having computer-executable instructions embodied thereon isprovided for processing an electronic disbursement by a disbursementmodule (DM) computer device. The DM computer device includes a memorydevice and a processor. When executed by the processor, thecomputer-executable instructions cause the processor to register a payorwith a disbursement service provided by the DM computer device and toreceive a disbursement command from the payor. The disbursement commandinstructs a disbursement to be made to a payee and includes payeecontact information, payee verification data, and a disbursement amount.The processor is further programmed to receive a disbursement requestmessage that includes a payee identifier from the payee requesting thatthe disbursement be made, and to verify the payee by matching the payeeidentifier to the payee verification data. The processor is furtherprogrammed to electronically transfer funds from a bank accountassociated with the payor to a bank account associated with the payee.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-14 show exemplary embodiments of the method and system describedherein.

FIG. 1 is a schematic diagram illustrating an exemplary multi-partypayment card industry system for enabling ordinary payment-by-cardtransactions in which merchants and card issuers do not necessarily havea one-to-one relationship.

FIG. 2 is a simplified block diagram of an exemplary payment cardaccount system having a Disbursement Module (DM) in accordance with oneembodiment of the present invention.

FIG. 3 is an expanded block diagram of an exemplary embodiment of aserver architecture of the payment card account system shown in FIG. 2.

FIG. 4 illustrates an exemplary configuration of a cardholder computerdevice operated by a cardholder such as the computer devices shown inFIGS. 2 and 3.

FIG. 5 illustrates an exemplary configuration of a server computerdevice such as the server system shown in FIGS. 2 and 3.

FIG. 6 is a simplified data flow block diagram of a customer registeringwithin an exemplary DM payment account system to receive a disbursementin accordance with one embodiment of the present invention.

FIG. 7 is a simplified data flow block diagram of a disbursementtransaction being processed by a DM payment account system in accordancewith one embodiment of the present invention.

FIG. 8 is a flowchart showing a disbursement transaction being processedby a DM payment account system from the perspective of a company newlyregistering for a disbursement service.

FIG. 9 is a flowchart showing a disbursement transaction being processedby a DM payment account system from the perspective of a customer, whois not previously registered with an electronic wallet application ofthe DM payment system.

FIG. 10 is a flowchart showing a disbursement transaction beingprocessed by a DM payment account system from the perspective of acustomer, who is previously registered with an electronic walletapplication of the DM payment system.

FIG. 11 is a flowchart showing a disbursement transaction beingprocessed by a DM payment account system from the perspective of acustomer, who is having a claim processed onsite by a business entityand who is not previously registered with an electronic walletapplication of the DM payment system.

FIG. 12 is a flowchart showing a disbursement transaction beingprocessed by a DM payment account system from the perspective of acustomer, who is having a claim processed onsite while meeting with acustomer representative associated with a business entity and who is notpreviously registered with an electronic wallet application of the DMpayment system.

FIG. 13 is a flowchart showing a disbursement transaction beingprocessed by a DM payment account system from the perspective of acustomer, who is having a claim processed remotely by a business entityand who is not previously registered with an electronic walletapplication of the DM payment system.

FIG. 14 is a flowchart showing a disbursement transaction beingprocessed by a DM payment account system from the perspective of acustomer, who is having a claim processed remotely by a business entityand who is previously registered with an electronic wallet applicationof the DM payment system.

DETAILED DESCRIPTION OF THE DISCLOSURE

Embodiments of the methods and systems described herein include apayment card account system having a disbursement module (DM) (referredto herein collectively as the “DM payment system”) that enables thesystem to offer a disbursement service to at least one of merchants,cardholders and issuers. In one embodiment, the DM payment systemenables a business, such as an insurance company, governmental entity,or other business entity, to register with the DM payment system, andthen make electronic payments to its customers (e.g., an insured, aconstituent, or other customer). A business or entity making a paymentmay be referred to as “payor” and the customer or the party receivingthe payment may be referred to as “payee”.

For example, in the scenario where a business entity is looking to usethe DM payment system for making payments (i.e., disbursements) to itscustomers, the business entity accesses a website associated with thepayment card interchange network. The business entity registers with thepayment card network for the DM service by entering payor registrationdata. After the business entity registers for the DM service, thebusiness entity downloads certain computer code from the payment cardnetwork to a business entity computer device for displaying adisbursement button on a website associated with the business entity. Asexplained below in more detail, the disbursement button is displayed onthe business entity website so that a customer representative of thebusiness entity can initiate a disbursement to a customer.

Continuing with the example from above, after the business entity hasregistered for the DM service and the disbursement button has beendownloaded onto the business entity website, a customer representativeassociated with the business entity may prepare an internal form forprocessing and making a disbursement to a customer. In the exampleembodiment, the internal form is displayed on the business entitycomputer device and accessible by the customer representative. Forexample, the business entity could be an insurance company that mustmake a disbursement to a policyholder for a claim. In that case, thecustomer representative logs into the insurance company computingsystem, accesses a claim disbursement form online, enters the requiredinformation into the disbursement form including capturing the customer(i.e., policyholder) contact information such as a mobile phone numberand/or email address for the customer, and selects the DM disbursementbutton displayed on the insurance company website. The customer contactinformation and an optional payment verification identifier (i.e., claimID) are then communicated as a disbursement command from the insurancecompany computing system to the DM payment system for processing. If aclaim ID is generated, the claim ID is provided to the customer in anemail or by other means to be used as a validation for payment.

In another embodiment, the disbursements can be uploaded as a batchfile. In the case of a batch disbursement, a customer representative forthe business entity prepares the online internal forms to make thedisbursements, and selects the DM disbursement button displayed on thebusiness entity website. At a designated time (i.e., daily, weekly,etc.), the disbursement commands are transmitted, typically in an XMLformat, to the DM payment system for processing. Each disbursementcommand of the batch disbursement commands contains a contact email ormobile phone number for the customer/payee. In some cases, thedisbursement command transmitted to the DM payment system also includesa claim ID for customer validation. If there is a claim ID, the claim IDis provided to the customer/payee in an email or by other means (paymentverification message) so that it can be used by the customer to validatepayment.

It is important to note that at this point the customer or payee doesnot need to be signed up for receiving an electronic disbursement. Inother words, the insurance company representative can prepare thedisbursement form online, enter the required information into thedisbursement form including capturing the customer (i.e., policyholder)contact information such as a mobile phone number and/or email addressfor the customer, and select the DM disbursement button displayed on theinsurance company website without the customer being registered withinthe system for receiving payment.

After the company has uploaded the disbursement commands into the DMpayment system including a contact email or mobile phone number for thecustomer, and an amount ($X) to be paid to the customer, a paymentverification message is automatically sent to the customer via thecustomer contact data (email, text message, push alert). The paymentverification message may also include a link to the insurance companywebsite. Accordingly, the customer accesses the website of the insurancecompany based on the commands in the payment message, and then validatesthe claim number with the claim ID. The website includes a link for thecustomer to register with the DM payment system. In the exampleembodiment, the DM payment system would include a payment processingapplication, sometimes referred to as an electronic wallet applicationthat the customer would register with by entering customer registrationdata including a receiving PAN (Primary Account Number) or bank accountnumbers along with any payment PANs or bank account numbers. If thecustomer does not have an eligible account, the customer will beprompted to register for a prepaid card associated with the DM paymentsystem.

In the example embodiment, the wallet application provides the receivingPAN entered by the customer to the business entity (i.e., the insurancecompany) for payment processing. The payment processing can utilize apayment system such as MasterCard® MoneySend™ (MasterCard and MoneySendare trademarks of MasterCard International Incorporated located inPurchase, N.Y.), an Automated Clearing House (ACH) account, or any otherpayment processing account. The company then initiates the paymenttransaction within the DM payment system, and the customer receives anelectronic payment either by the funds being transferred to the customerreceiving PAN, the customer bank account, or a retail location forcustomer pickup, or being transferred to a prepaid credit card that thecustomer can use.

Accordingly, the DM payment system enables a user, such a businessentity, to electronically disburse funds to a customer using anelectronic wallet computer application and the payment card system,wherein the funds are transferred over the payment network from anaccount associated with the business entity to an account or a prepaidpayment card associated with the customer. The DM payment system enablesa business entity to quickly make a payment to the customer withoutincurring the costs associated with issuing a check.

The methods and systems described herein may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof,wherein the technical effect may include at least one of: (i) thecompany accesses a website associated with the payment card interchangenetwork, the website including an electronic wallet application; (ii)the company registers with the electronic wallet application by enteringpayor registration data; (iii) company downloads a disbursement buttonfrom the payment card network for display on the company website ortablet application; (iv) a customer representative associated with thecompany prepares an internal form for processing and making adisbursement to the customer including capturing the customer contactinformation such as a mobile phone number and/or email address; (v) thecompany representative selects the DM disbursement button displayed onthe company website; (vi) a message is communicated to the customer perthe customer contact information advising the customer that a payment isready, wherein the message may include a link to the company website anda payment verification identifier (i.e., claim ID); (vii) the customeraccesses the company website per the message and verifies the claim byentering the claim ID; (viii) the customer clicks on a link to theelectronic wallet application and registers therewith if not alreadyregistered, wherein the customer provides customer registration dataincluding customer contact data, a receiving PAN (Primary AccountNumber) or bank account numbers, any payment PANs or bank accountnumbers for the customer, and/or (optionally) register for a prepaidcard; (ix) the company receives the customer registration data throughthe electronic wallet application; (x) the company initiates thedisbursement transaction by instructing the issuer bank to disburse thefunds to customer through the payment card interchange network; and (xi)the payment card network performs an authorization process andsettlement process to electronically transfer the funds from the companyto the customer.

The following detailed description illustrates embodiments of theinvention by way of example and not by way of limitation. Thedescription clearly enables one skilled in the art to make and use thedisclosure, describes several embodiments, adaptations, variations,alternatives, and uses of the disclosure, including what is presentlybelieved to be the best mode of carrying out the disclosure. Thedisclosure is described as applied to an exemplary embodiment, namely,systems and methods of validating cardholder information through thepayment card network for merchants in a payment card network. However,it is contemplated that this disclosure has general application tocomputing systems in industrial, commercial, and residentialapplications.

Although the DM payment system may be described herein in the context ofuse by an insurance company, it is not limited to this particular use.Accordingly, the DM payment system may be used in other embodiments,including any other entity making payments or disbursements to itscustomers.

As used herein, an element or step recited in the singular and precededwith the word “a” or “an” should be understood as not excluding pluralelements or steps, unless such exclusion is explicitly recited.Furthermore, references to “one embodiment” of the present invention arenot intended to be interpreted as excluding the existence of additionalembodiments that also incorporate the recited features.

Embodiments of the present invention described herein relate tovalidating cardholder information through the payment card network formerchants in payment card transactions, such as, card-not-presentpayment card transactions.

FIG. 1 is a schematic diagram 20 illustrating an exemplary multi-partypayment card industry system for enabling ordinary payment-by-cardtransactions in which merchants and card issuers do not necessarily havea one-to-one relationship. The present invention relates to a paymentcard system, such as a credit card payment system using the MasterCard®payment system. The MasterCard® payment system is a proprietarycommunications standard promulgated by MasterCard InternationalIncorporated® for the exchange of financial transaction data betweenfinancial institutions that are members of MasterCard InternationalIncorporated®. (MasterCard is a registered trademark of MasterCardInternational Incorporated located in Purchase, New York).

In a typical payment card system, a financial institution such as anissuer 21 issues a payment account card, such as a credit card accountor a debit card account, to a cardholder 22, who uses the paymentaccount card to tender payment for a purchase from a merchant 24. Toaccept payment with the payment account card, merchant 24 must normallyestablish an account with a financial institution that is part of thefinancial payment system. This financial institution is usually calledthe “merchant bank” or the “acquiring bank” or “acquirer bank.” When acardholder 22 tenders payment for a purchase with a payment account card(also known as a financial transaction card), merchant 24 requestsauthorization from merchant bank 26 for the amount of the purchase. Therequest may be performed over the telephone, but is usually performedthrough the use of a point-of-sale terminal, which reads thecardholder's account information from the magnetic stripe on the paymentaccount card and communicates electronically with the transactionprocessing computers of merchant bank 26. Alternatively, merchant bank26 may authorize a third party to perform transaction processing on itsbehalf. In this case, the point-of-sale terminal will be configured tocommunicate with the third party. Such a third party is usually called a“merchant processor” or an “acquiring processor.”

Using a network interface processor 28, the computers of the merchantbank or the merchant processor will communicate with the computers ofissuer 30 to determine whether the cardholder's account is in goodstanding and whether the purchase is covered by the cardholder'savailable credit line or account balance. Based on these determinations,the request for authorization will be declined or accepted. If therequest is accepted, an authorization code is issued to merchant 24.

When a request for authorization is accepted, the available credit lineor available balance of cardholder's account 32 is decreased. Normally,a charge is not posted immediately to a cardholder's account becausebankcard associations, such as MasterCard International Incorporated®,have promulgated rules that do not allow a merchant to charge, or“capture,” a transaction until goods are shipped or services aredelivered. When a merchant ships or delivers the goods or services,merchant 24 captures the transaction by, for example, appropriate dataentry procedures on the point-of-sale terminal. If a cardholder cancelsa transaction before it is captured, a “void” is generated. If acardholder returns goods after the transaction has been captured, a“credit” is generated.

For debit card transactions, when a request for a PIN authorization isapproved by the issuer, the cardholder's account 32 is decreased.Normally, a charge is posted immediately to cardholder's account 32. Thebankcard association then transmits the approval to the acquiringprocessor for distribution of goods/services, or information or cash inthe case of an ATM.

After a transaction is captured, the transaction is settled betweenmerchant 24, merchant bank 26, and issuer 30. Settlement refers to thetransfer of financial data or funds between the merchant's account,merchant bank 26, and issuer 30 related to the transaction. Usually,transactions are captured and accumulated into a “batch,” which issettled as a group.

Financial transaction cards or payment account cards can refer to creditcards, debit cards, and prepaid cards. These cards can all be used as amethod of payment for performing a transaction. As described herein, theterm “financial transaction card” or “payment account card” includescards such as credit cards, debit cards, and prepaid cards, but alsoincludes any other devices that may hold payment account information,such as mobile phones, personal digital assistants (PDAs), and key fobs.

FIG. 2 is a simplified block diagram of an exemplary payment cardaccount system 100 having a Disbursement Module (DM) and offering adisbursement service in accordance with one embodiment of the presentinvention. System 100 is a payment card account system, which can beutilized by account holders as part of a process of initiating anauthorization request and performing a transaction as described below.In addition, system 100 is a payment card account system having a DM,which enables a first user (e.g., merchant, business entity, etc.) toregister with the system and initiate an electronic disbursement paymentto a second user (e.g., customer, etc.) as described below. Therefore,payment card system 100 can also be referred to as a DM payment system.

More specifically, in the example embodiment, system 100 includes aserver system 112, which is a type of computer system, and a pluralityof client sub-systems (also referred to as client systems 114) connectedto server system 112. In one embodiment, client systems 114 arecomputers including a web browser and a memory device, such that serversystem 112 is accessible to client systems 114 using the Internet.Client systems 114 are interconnected to the Internet through manyinterfaces including a network, such as a local area network (LAN) or awide area network (WAN), dial-in-connections, cable modems, and specialhigh-speed ISDN lines. Client systems 114 could be any device capable ofinterconnecting to the Internet including a web-based phone, personaldigital assistant (PDA), or other web-based connectable equipment.

System 100 also includes point-of-sale (POS) terminals 115, which areconnected to client systems 114 and may be connected to server system112. POS terminals 115 are interconnected to the Internet through manyinterfaces including a network, such as a local area network (LAN) or awide area network (WAN), dial-in-connections, cable modems, wirelessmodems, and special high-speed ISDN lines. POS terminals 115 could beany device capable of interconnecting to the Internet and including aninput device capable of reading information from a cardholder'sfinancial transaction card.

A database server 116 is connected to database 120, which containsinformation on a variety of matters, as described below in greaterdetail. In one embodiment, centralized database 120 is stored on serversystem 112 and can be accessed by cardholders at one of client systems114 by logging onto server system 112 through one of client systems 114.In an alternative embodiment, database 120 is stored remotely fromserver system 112 and may be non-centralized. Database 120 may storetransaction data generated as part of sales activities conducted overthe bankcard network including data relating to merchants, accountholders or customers, and purchases. Database 120 may also store accountdata including at least one of a cardholder name, a cardholder address,an account number, and other account identifiers. Database 120 may alsostore merchant data including a merchant identifier that identifies eachmerchant registered to use the payment account card network, andinstructions for settling transactions including merchant bank accountinformation. Database 120 may also store PAN numbers or bank accountnumbers for various parties including merchants and customers, alongwith payment verification identifiers and other data necessary toimplement the system and processes described herein.

In one embodiment, a Disbursement Module (DM) 121 is in communicationwith server system 112. DM 121 enables system 100 to offer thedisbursement service, which includes enabling a merchant to disbursefunds electronically to a customer, and validating that the customer isthe appropriate party to receive those funds. Specifically, the merchantuploads disbursement commands to DM 121 including a disbursement amount,customer contact data, and a designated claim ID (or a paymentverification ID). The customer registers with an electronic walletapplication hosted by server system 112 which includes entering customerregistration data including requesting a prepaid payment card orproviding a receiving PAN for the customer, and providing a claim ID.The customer can register with the electronic wallet application usingone of client systems 114 or input device 118. DM 121 then validates thecustomer entered claim ID by comparing it to the designated claim IDprovided in the disbursement commands. If the claim IDs match, thecustomer is validated for receiving the disbursement. An authorizationprocess and settlement process for transferring funds from the merchantto the customer are performed. The funds are transferred as requested bythe customer either to the customer receiving PAN account or to aprepaid payment card.

System 100 also includes at least one input device 118, which isconfigured to communicate with at least one of POS terminal 115, clientsystems 114 and server system 112. In the exemplary embodiment, inputdevice 118 is associated with or controlled by a cardholder making apurchase using a payment card account and payment card account system100. Input device 118 is interconnected to the Internet through manyinterfaces including a network, such as a local area network (LAN) or awide area network (WAN), dial-in-connections, cable modems, wirelessmodems, and special high-speed ISDN lines. Input device 118 could be anydevice capable of interconnecting to the Internet including a web-basedphone, personal digital assistant (PDA), or other web-based connectableequipment. Input device 118 is configured to communicate with POSterminal 115 using various outputs including, for example, Bluetoothcommunication, radio frequency communication, near field communication,network-based communication, and the like.

In the example embodiment, one of client systems 114 may be associatedwith an acquirer, a cardholder, or a customer; while another one ofclient systems 114 may be associated with an issuer; POS terminal 115may be associated with a merchant; input device may be associated with acardholder or a customer; and server system 112 may be associated withthe payment system network or the interchange network.

FIG. 3 is an expanded block diagram of an exemplary embodiment of aserver architecture of a payment card account system 122 having aDisbursement Module (DM) and offering a disbursement service inaccordance with one embodiment of the present invention. Components insystem 122, identical to components of system 100 (shown in FIG. 2), areidentified in FIG. 3 using the same reference numerals as used in FIG.2. System 122 includes server system 112, client systems 114, POSterminals 115, and input devices 118. Server system 112 further includesdatabase server 116, a transaction server 124, a web server 126, a faxserver 128, a directory server 130, and a mail server 132. A storagedevice 134 is coupled to database server 116 and directory server 130.Servers 116, 124, 126, 128, 130, and 132 are coupled in a local areanetwork (LAN) 136. In addition, a system administrator's workstation138, a cardholder's workstation 140, and a supervisor's workstation 142are coupled to LAN 136. Alternatively, workstations 138, 140, and 142are coupled to LAN 136 using an Internet link or are connected throughan Intranet.

Each workstation, 138, 140, and 142 is a personal computer having a webbrowser. Although the functions performed at the workstations typicallyare illustrated as being performed at respective workstations 138, 140,and 142, such functions can be performed at one of many personalcomputers coupled to LAN 136. Workstations 138, 140, and 142 areillustrated as being associated with separate functions only tofacilitate an understanding of the different types of functions that canbe performed by individuals having access to LAN 136.

Server system 112 is configured to be communicatively coupled to variousindividuals, including employees 144 and to third parties, e.g., accountholders, customers, auditors, etc., 146 using an ISP Internet connection148. The communication in the exemplary embodiment is illustrated asbeing performed using the Internet, however, any other wide area network(WAN) type communication can be utilized in other embodiments, i.e., thesystems and processes are not limited to being practiced using theInternet. In addition, and rather than WAN 150, local area network 136could be used in place of WAN 150.

In the exemplary embodiment, any authorized individual having aworkstation 154 can access system 122. At least one of the clientsystems includes a manager workstation 156 located at a remote location.Workstations 154 and 156 are personal computers having a web browser.Also, workstations 154 and 156 are configured to communicate with serversystem 112. Furthermore, fax server 128 communicates with remotelylocated client systems, including a client system 156 using a telephonelink. Fax server 128 is configured to communicate with other clientsystems 138, 140, and 142 as well.

In the example embodiment, server system 112 is in communication with DM121. DM 121 enables system 122 to offer the disbursement service, whichincludes enabling a merchant to disburse funds electronically to acustomer, and validating that the customer is the appropriate party toreceive those funds.

FIG. 4 illustrates an exemplary configuration of a cardholder's'computer device 202 operated by a cardholder's 201. Cardholder'scomputer device 202 may include, but is not limited to, client systems114, 138, 140, and 142, POS terminal 115, input device 118, workstation154, and manager workstation 156 (shown in FIG. 3).

Cardholder's computer device 202 includes a processor 205 for executinginstructions. In some embodiments, executable instructions are stored ina memory area 210. Processor 205 may include one or more processingunits (e.g., in a multi-core configuration). Memory area 210 is anydevice allowing information such as executable instructions and/or otherdata to be stored and retrieved. Memory area 210 may include one or morecomputer readable media.

Cardholder's computer device 202 also includes at least one media outputcomponent 215 for presenting information to cardholder's 201. Mediaoutput component 215 is any component capable of conveying informationto cardholder's 201. In some embodiments, media output component 215includes an output adapter such as a video adapter and/or an audioadapter. An output adapter is operatively coupled to processor 205 andoperatively couplable to an output device such as a display device(e.g., a liquid crystal display (LCD), organic light emitting diode(OLED) display, cathode ray tube (CRT), or “electronic ink” display) oran audio output device (e.g., a speaker or headphones).

In some embodiments, cardholder's computer device 202 includes an inputdevice 220 for receiving input from cardholder's 201. Input device 220may include, for example, a keyboard, a pointing device, a mouse, astylus, a touch sensitive panel (e.g., a touch pad or a touch screen), agyroscope, an accelerometer, a position detector, or an audio inputdevice. A single component such as a touch screen may function as bothan output device of media output component 215 and input device 220.

Cardholder's computer device 202 may also include a communicationinterface 225, which is communicatively couplable to a remote devicesuch as server system 112. Communication interface 225 may include, forexample, a wired or wireless network adapter or a wireless datatransceiver for use with a mobile phone network (e.g., Global System forMobile communications (GSM), 3G, 4G or Bluetooth) or other mobile datanetwork (e.g., Worldwide Interoperability for Microwave Access (WIMAX)).

Stored in memory area 210 are, for example, computer readableinstructions for providing a user interface to cardholder's 201 viamedia output component 215 and, optionally, receiving and processinginput from input device 220. A user interface may include, among otherpossibilities, a web browser and client application. Web browsers enablecardholder's, such as cardholder's 201, to display and interact withmedia and other information typically embedded on a web page or awebsite from server system 112. A client application allows cardholder's201 to interact with a server application from server system 112.

FIG. 5 illustrates an exemplary configuration of a server computerdevice 275 such as server system 112 (shown in FIGS. 2 and 3). Servercomputer device 275 may include, but is not limited to, database server116, transaction server 124, web server 126, fax server 128, directoryserver 130, and mail server 132.

Server computer device 275 includes a processor 280 for executinginstructions. Instructions may be stored in a memory area 285, forexample. Processor 280 may include one or more processing units (e.g.,in a multi-core configuration).

Processor 280 is operatively coupled to a communication interface 290such that server computer device 275 is capable of communicating with aremote device such as cardholder's computer device 202 or another servercomputer device 275. For example, communication interface 290 mayreceive requests from client systems 114 or input device 118 via theInternet, as illustrated in FIGS. 2 and 3.

Processor 280 may also be operatively coupled to a storage device 134.Storage device 134 is any computer-operated hardware suitable forstoring and/or retrieving data. In some embodiments, storage device 134is integrated in server computer device 275. For example, servercomputer device 275 may include one or more hard disk drives as storagedevice 134. In other embodiments, storage device 134 is external toserver computer device 275 and may be accessed by a plurality of servercomputer devices 275. For example, storage device 134 may includemultiple storage units such as hard disks or solid state disks in aredundant array of inexpensive disks (RAID) configuration. Storagedevice 134 may include a storage area network (SAN) and/or a networkattached storage (NAS) system.

In some embodiments, processor 280 is operatively coupled to storagedevice 134 via a storage interface 295. Storage interface 295 is anycomponent capable of providing processor 280 with access to storagedevice 134. Storage interface 295 may include, for example, an AdvancedTechnology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, aSmall Computer System Interface (SCSI) adapter, a RAID controller, a SANadapter, a network adapter, and/or any component providing processor 280with access to storage device 134.

Memory areas 210 and 285 may include, but are not limited to, randomaccess memory (RAM) such as dynamic RAM (DRAM) or static RAM (SRAM),read-only memory (ROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), andnon-volatile RAM (NVRAM). The above memory types are exemplary only, andare thus not limiting as to the types of memory usable for storage of acomputer program.

FIG. 6 is a simplified data flow block diagram 600 of a customerregistering within a DM payment system 100 (see FIG. 2) to receive adisbursement in accordance with one embodiment of the present invention.Components in diagram 600 that are identical to components of system 100(shown in FIG. 2) are identified in FIG. 6 using the same referencenumerals as used in FIG. 2.

In the example embodiment, a customer 602 interacts with a company 604,such as a business, an insurance company, a governmental entity, orother business entity, that is already registered with DM payment system100. Specifically, customer 602 may interact 606 with a variety ofchannels of communication 608. Channels of communication 608 include,but are not limited to, a computer device such as client system 114, amobile device (e.g., smart phone or computer tablet) such as inputdevice 118, or a telephone.

In the example embodiment, customer 602 accesses 610 a websiteassociated with company 604, the website being displayed on one ofcommunication channels 608. The website displays a link to an electronicwallet application 612 hosted on a payment processing platform 614,which is part of the DM payment system 100. Payment processing platform614 includes server system 112, database 120 and DM 121. Electronicwallet application 612 interfaces between company 604 and paymentprocessing platform 614. Specifically, electronic wallet application 612receives and communicates data between a website associated with company604 and payment processing platform 614.

Customer 602 enters customer registration data 616 into electronicwallet application 612. To enter customer registration data 616, thewebsite associated with company 604 includes a website link thatconnects customer 602 either to an electronic wallet application 610website or a mobile wallet application. Customer registration data 616includes, but is not limited to, customer contact data, a receiving PAN(Primary Account Number) or bank account numbers, and any payment PANsor bank account numbers for the customer. If customer 602 does not havean eligible PAN, customer 602 will be prompted to register for a prepaidcard associated with DM payment system 100. Customer registration data616 is stored within database 120.

After receiving customer registration data 616, company 604 transfers618 funds to an issuer bank 620. The funds transferred are to be used,at least in part, for completing the disbursement to customer 602. Inone embodiment, company 604 also transfers at least a portion ofcustomer registration data 616, namely the receiving PAN of thecustomer, to issuer bank 620, which in turn is communicated to paymentprocessing platform 614. In an alternate embodiment, DM payment systemprocesses customer registration data.

FIG. 7 is a simplified data flow block diagram 700 of a disbursementtransaction being processed by a DM payment system 100 (see FIG. 2) inaccordance with one embodiment of the present invention. Components indiagram 700 that are identical to components already identified inearlier figures are identified using the same reference numeralspreviously used.

In the example embodiment, after company 604 receives customerregistration data 616 from customer 602 through electronic walletapplication 612 and customer 602 provides the necessary paymentverification identifier, company 604 initiates 702 the disbursementtransaction by instructing issuer bank 620 to disburse the funds tocustomer 602. In an alternate embodiment, DM payment system 100instructs issuer bank 620 to disburse the funds to customer 602. Inanother alternate embodiment, DM payment system 100 may directly submitthe payment to customer 602 upon receiving the payment verificationidentifier.

In the example embodiment, issuer bank 620 transmits an authorizationrequest message 704 (message 0200) to payment processing platform 614,which in turn communicates authorization request message 704 (message0200) to a receiving bank 706. Receiving bank 706 is associated with andcorresponds to the receiving PAN of customer 602. Upon receivingauthorization request message 704, receiving bank 706 verifies theexistence in good standing of the receiving PAN of customer 602 or, inthe case where customer 602 has registered to receive the disbursementvia a prepaid card, verifies that receiving bank 706 is capable ofissuing the requested prepaid card to customer 602.

After completing the verification process, receiving bank 706 transmitsan authorization response message 708 (message 0210) to paymentprocessing platform 614, which in turn communicates authorizationresponse message 708 (message 0210) to issuer bank 620. If receivingbank 706 is able to affirmatively verify that the receiving PAN ofcustomer 602 exists and is in good standing or that a prepaid card canbe issued to customer 602, then authorization response message 708 is aconfirmation message to complete the disbursement. If, however,receiving bank 706 is not able to affirmatively verify the receiving PANor that a prepaid card can be issued to customer 602, then authorizationresponse message 708 is a denial message and the disbursement iscancelled and another form of payment is requested.

After receiving a confirming authorization response message 708, paymentprocessing platform 614 transmits a disbursement message 710 toreceiving bank 706. Disbursement message 710 includes instructions totransfer funds from issuer bank 620 to receiving bank 706. Morespecifically, disbursement message 710 includes instructions to transferfunds from a payment account associated with company 604 at issuer bank620 to a receiving account or prepaid payment card associated withcustomer 602 at receiving bank 706. Customer 602 has then received thedisbursement payment from company 604.

FIG. 8 is a flowchart 800 showing a disbursement transaction beingprocessed by a DM payment system 100 (FIG. 2) from the perspective of acompany 802 newly registering for the disbursement service. In theexample embodiment, company 802 is an insurance company making adisbursement to an insured 804 for a property loss associated with aninsurance policy. However, the invention is not limited to this example.The invention could be used by any business entity making a payment to aperson.

In the example embodiment, insurance company 802 accesses 806 a websiteassociated with payment card interchange network 100. Specifically,insurance company 802 access 806 an electronic wallet application hostedby payment card interchange network 100. Insurance company 802 registers808 with payment card network 100 for the DM service by entering payorregistration data. Insurance company 802 then downloads 810 certaincomputer code from payment card network 100 to a business entitycomputer device for displaying a disbursement button on a websiteassociated with insurance company 802. As explained below in moredetail, the disbursement button is displayed on the insurance companywebsite so that a customer representative may initiate a disbursement toinsured 804.

After downloading 810, a customer representative associated withinsurance company 802 prepares 812 an internal form for processing andmaking a disbursement to insured 804. The internal form is displayed ona computer device associated with insurance company 802 and accessibleby the customer representative. The customer representative accesses aclaim disbursement form online, enters the required information into thedisbursement form including capturing the customer (i.e., insured)contact information such as a mobile phone number and/or email addressfor insured 804, and selects the DM disbursement button displayed on theinsurance company website. The customer contact information and anoptional payment verification identifier (i.e., claim ID) are thencommunicated 814 as a disbursement command from insurance company 802computing system to DM payment system 100 for processing. If a claim IDis generated, the claim ID is provided 816 to insured 804 in an email orby other means to be used as a validation for payment.

In another embodiment, the disbursements can be uploaded as a batchfile. In the case of a batch disbursement, a customer representative forthe business entity prepares the online internal forms to make thedisbursements, and selects the DM disbursement button displayed on thebusiness entity website. At a designated time (i.e., daily, weekly,etc.), the disbursement commands are transmitted, typically in an XMLformat, to DM payment system 100 for processing. Each disbursementcommand of the batch disbursement commands contains a contact email ormobile phone number for the customer/payee. In some cases, thedisbursement command transmitted to DM payment system 100 also includesa claim ID for customer validation. If there is a claim ID, the claim IDis provided to the customer/payee in an email or by other means (paymentverification message) so that it can be used by the customer to validatepayment.

It is important to note that at this point insured/customer 804 or payeedoes not need to be signed up for receiving an electronic disbursement.In other words, representatives for insurance company 802 can prepare812 the disbursement form online, enter the required information intothe disbursement form including capturing the customer (i.e., insured)contact information such as a mobile phone number and/or email addressfor the customer, and select the DM disbursement button displayed on theinsurance company website without insured 804 being registered withinsystem 100 for receiving payment.

FIG. 9 is a flowchart 900 showing a disbursement transaction beingprocessed by a DM payment system 100 (FIG. 2) from the perspective of aninsured 902, who is not previously registered with the electronic walletapplication of DM payment system 100 that is displayed on a websiteassociated with insurance company 904. Insured 902 plans to access theelectronic wallet application using an insured computer device and aweb-based network connection linked to an insurance company computingdevice hosting the insurance company website.

In the example embodiment, insured 902 is due money from insurancecompany 904. Insured 902 receives 906 instructions in email or regularmail on how to receive the electronic disbursement from insurancecompany 904 (i.e., a computer link to click on to access the insurancecompany website). Insured 902 also receives 908 a payment verificationidentifier to validate claim and verify that insured 902 is the approvedperson to receive the disbursement.

Insured 902 then accesses 910 the website associated with insurancecompany 904 based on received 906 commands. The website associated withinsurance company 904 prompts insured 902 to validate 912 the claim byentering the payment verification identifier previously provided toinsured 902. Insured is then prompted to register 914 with DM paymentsystem 100 by entering customer registration data into the electronicwallet application. The customer registration data includes a receivingPAN (Primary Account Number) or bank account numbers along with anypayment PANs or bank account numbers. If insured 902 does not have aneligible PAN, the insured 902 will be prompted to register 916 for aprepaid card associated with DM payment system 100.

In the example embodiment, upon registration by insured 902, DM paymentsystem 100 initiates 918 payment to insured 902. Because DM paymentsystem 100 initiates payment, the security of payment informationassociated with insured 902 is improved since it is not transmittedand/or shared among multiple entities. In an alternate embodiment, thewallet application may provide the receiving bank account number enteredby insured 902 to insurance company 904 for payment processing.Insurance company 904 may then initiate the payment transaction withinDM payment system 100, and insured 902 would receive an electronicpayment either by the funds being transferred to the customer receivingbank account number, or being transferred to a prepaid credit card thatthe customer can use.

FIG. 10 is a flowchart 1000 showing a disbursement transaction beingprocessed by a DM payment system 100 (FIG. 2) from the perspective of aninsured 1002, who is already registered 1004 with the electronic walletapplication of DM payment system 100 that is displayed on a websiteassociated with insurance company 1006. Insured 1002 accesses theelectronic wallet application using an insured computer device and aweb-based network connection linked to an insurance company computingdevice hosting the insurance company website.

In the example embodiment, insured 1002 is due money from insurancecompany 1006. Insured 1002 receives 1008 instructions in email orregular mail on how to receive the electronic disbursement frominsurance company 1006 (i.e., a computer link to click on to access theinsurance company website). Insured 1002 also receives 1010 a paymentverification identifier to validate claim and verify that insured 1002is the approved person to receive the disbursement.

Insured 1002 then accesses 1012 the website associated with insurancecompany 1006 based on received 1008 instructions. The website associatedwith insurance company 1006 provides a link for insured 1002 to login tothe electronic wallet application of DM payment system 100 so thatinsured 1002 can receive the payment.

Insured 1002 clicks 1014 on the link and enters login data for insured1002. The electronic wallet application authenticates 1016 insured 1002and returns receiving bank account number to insurance company computingdevice for disbursement processing. Insurance company 1006 processes thepayment as described in FIG. 7, and the appropriate funds aretransferred to insured 1002. The funds are either transferred to anaccount associated with the receiving bank account number of insured1002 or to a prepaid card for use by insured 1002.

FIG. 11 is a flowchart 1100 showing a disbursement transaction beingprocessed by a DM payment system 100 (FIG. 2) from the perspective of aninsured 1102, who is having a claim processed onsite by an insurancecompany 1104 and who is not previously registered with the electronicwallet application of DM payment system 100.

In the example embodiment, insured 1102 is due money from insurancecompany 1104. Insured 1102 visits 1106 a company representative ofinsurance company 1104. Insurance company 1104 provides 1108 a tabletcomputer or a mobile computing device to insured 1102. The mobilecomputing device includes an application or link to the electronicwallet application. Insured 1102 registers 1110 with the electronicwallet application by entering customer registration data into theelectronic wallet application. The customer registration data includes areceiving PAN (Primary Account Number) or bank account numbers alongwith any payment PANs or bank account numbers.

In the example embodiment, the wallet application provides 1112 thereceiving PAN entered by insured 1102 to insurance company 1104 forpayment processing. Insurance company 1104 then initiates 1114 thepayment transaction within DM payment system 100, and insured 1102receives an electronic payment either by the funds being transferred tothe customer receiving bank account number or by prepaid payment card.

FIG. 12 is a flowchart 1200 showing a disbursement transaction beingprocessed by a DM payment system 100 (FIG. 2) from the perspective of aninsured 1202, who is having a claim processed onsite while meeting withan insurance adjuster associated with an insurance company 1204 and whois not previously registered with the electronic wallet application ofDM payment system 100.

In the example embodiment, insured 1202 is due money from insurancecompany 1204. Insured 1202 visits 1206 a company representative ofinsurance company 1204. Insurance company 1104 provides 1108 anapplication on a computer tablet or mobile computing device with a linkto the electronic wallet application. Insured 1202 clicks 1210 on thelink and registers 1212 with the electronic wallet application byentering customer registration data into the electronic walletapplication. The customer registration data includes a receiving PAN(Primary Account Number) or bank account numbers along with any paymentPANs or bank account numbers.

In the example embodiment, the wallet application provides 1214 thereceiving PAN entered by insured 1202 to insurance company 1204 forpayment processing. Insurance company 1204 then initiates 1216 thepayment transaction within DM payment system 100, and insured 1202receives an electronic payment either by the funds being transferred tothe customer receiving bank account number or by prepaid payment card.

FIG. 13 is a flowchart 1300 showing a disbursement transaction beingprocessed by a DM payment system 100 (FIG. 2) from the perspective of aninsured 1302, who is having a claim processed remotely by an insurancecompany 1304 and who is not previously registered with the electronicwallet application of DM payment system 100. Insured 1302 is using amobile computing device and is meeting with an insurance adjuster at thetime of the payment.

In the example embodiment, insured 1302 is due money from insurancecompany 1304. Insurance company 1304 sends 1306 a text or email toinsured 1302 mobile device instructing insured 1302 to pick up money.The text or email includes a link to download 1308 the electronic walletapplication. Insured 1302 registers 1310 with the electronic walletapplication by entering customer registration data into the electronicwallet application. The customer registration data includes a receivingPAN (Primary Account Number) or bank account numbers along with anypayment PANs or bank account numbers.

Insured 1302 views 1312 claim disbursement from insurance company 1304and validates 1314 claim by entering payment verification identifier. Inthe example embodiment, upon registration by insured 1302, DM paymentsystem 100 initiates 1316 payment to insured 1302. Because DM paymentsystem 100 initiates payment, the security of payment informationassociated with insured 1302 is improved (i.e., the transaction is moresecure) since it is not transmitted and/or shared among multipleentities. In an alternate embodiment, the wallet application may providethe receiving bank account number entered by insured 1302 to insurancecompany 1304 for payment processing. Insurance company 1304 may theninitiate the payment transaction within DM payment system 100, andinsured 1302 would receive an electronic payment either by the fundsbeing transferred to the customer receiving bank account number or byprepaid payment card.

FIG. 14 is a flowchart 1400 showing a disbursement transaction beingprocessed by a DM payment system 100 (FIG. 2) from the perspective of aninsured 1402, who is having a claim processed remotely by an insurancecompany 1404 and who is previously registered with the electronic walletapplication of DM payment system 100. Insured 1402 is using a mobilecomputing device and is meeting with an insurance adjuster at the timeof the payment.

In the example embodiment, insured 1402 is due money from insurancecompany 1404. Insurance company 1404 sends 1406 a text or email toinsured 1402 mobile device instructing insured 1402 to pick up money.The text or email includes a link to the electronic wallet application.Insured 1402 clicks 1408 on the link and accesses the electronic walletapplication using login and passwords. The customer registration data isalready saved in the electronic wallet application.

Insured 1402 views 1410 claim disbursement from insurance company 1404and validates 1412 claim by entering payment verification identifier.The wallet application provides 1414 the receiving bank account numberentered by insured 1402 and save in the system to insurance company 1404for payment processing. Insurance company 1404 then initiates 1416 thepayment transaction within DM payment system 100, and insured 1402receives an electronic payment either by the funds being transferred tothe customer receiving bank account number or by prepaid payment card.

The term processor, as used herein, refers to central processing units,microprocessors, microcontrollers, reduced instruction set circuits(RISC), application specific integrated circuits (ASIC), logic circuits,and any other circuit or processor capable of executing the functionsdescribed herein.

As used herein, the terms “software” and “firmware” are interchangeable,and include any computer program stored in memory for execution byprocessors 205, 280 including RAM memory, ROM memory, EPROM memory,EEPROM memory, and non-volatile RAM (NVRAM) memory. The above memorytypes are exemplary only, and are thus not limiting as to the types ofmemory usable for storage of a computer program.

As will be appreciated based on the foregoing specification, theabove-described embodiments of the disclosure may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof,wherein the technical effect is verifying by the issuer certain dataelements known to the merchant or acquired by the merchant during thetransaction. The merchant requests the verification service be performedand supplies the particular data to be verified. The issuer searches itsdatabases in an attempt to verify the data elements requested by themerchant. The issuer indicates whether the issuer was able to find amatch, did not find a match, or could not perform the verification byappending an indicator to the response message and returns the indicatorand an authorization decision to the merchant. Any such resultingprogram, having computer-readable code means, may be embodied orprovided within one or more computer-readable media, thereby making acomputer program product, i.e., an article of manufacture, according tothe discussed embodiments of the disclosure. The computer-readable mediamay be, for example, but is not limited to, a fixed (hard) drive,diskette, optical disk, magnetic tape, semiconductor memory such asread-only memory (ROM), and/or any transmitting/receiving medium such asthe Internet or other communication network or link. The article ofmanufacture containing the computer code may be made and/or used byexecuting the code directly from one medium, by copying the code fromone medium to another medium, or by transmitting the code over anetwork.

The above-described embodiments of a method and system of verifyingcertain data elements, selected by a merchant, by a transaction cardissuer for payment card transactions, including card-not-presenttransactions using a network interface processor provides acost-effective, secure, and reliable means for providing to a anincreased level of fraud risk avoidance to merchants using card-presentand card-not-present transactions.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal languages of the claims.

1-23. (canceled)
 24. A disbursement module (DM) computer device forprocessing an electronic disbursement, said DM computer devicecomprising: a memory device for storing data; and a processor incommunication with said memory device, said processor programmed to:register a payor with a disbursement service provided by said DMcomputer device using payor registration data received from a payorcomputer device associated with the payor; receive a disbursementrequest command from the payor computer device, wherein the disbursementrequest command instructs a disbursement notification message to be sentfrom said DM computer device to a payee, the disbursement requestcommand including payee contact information, payee verification data,and a disbursement amount to be paid to the payee, and wherein the payeeverification data includes a payee identifier; generate the disbursementnotification message including the payee identifier and a payor link,wherein the payor link is configured to direct the payee to a payorwebsite in response to selection of the payor link by the payee;automatically transmit the disbursement notification message to a payeecomputer device associated with the payee; register, via an electronicwallet application associated with said DM computer device, the payee inresponse to selection by the payee of an electronic wallet applicationlink displayed on the payor website, by receiving, from the payeecomputer device, an identification of at least one bank accountassociated with the payee for receiving the disbursement; receive adisbursement request message from the payee requesting that thedisbursement be made to the payee, the disbursement request messageincluding a candidate payee identifier; verify the payee by matching thecandidate payee identifier to the payee identifier received with thepayee verification data; and electronically transfer, in response to theregistration and the verification, funds from a bank account associatedwith the payor to the bank account associated with the payee.
 25. The DMcomputer device in accordance with claim 24, wherein the disbursementrequest command is one of a plurality of disbursement request commands,and wherein said processor is further programmed to: receive a batchfile including the plurality of disbursement request commands, each ofthe disbursement request commands identifying one of a correspondingplurality of payees; and generate the disbursement notification messageas one of a plurality of disbursement notification messages, each of thedisbursement notification messages corresponding to one of the pluralityof payees.
 26. The DM computer device in accordance with claim 25,wherein said processor is further programmed to: identify respectivepayee contact information and payee verification data of the pluralityof payees from within the batch file; and generate the disbursementnotification messages each including the corresponding payee identifierand a corresponding payor link.
 27. The DM computer device in accordancewith claim 24, wherein said processor is further programmed to: providea disbursement document for display on the payor computer device; promptthe payor to input data into the disbursement document; and receive thedata input into the disbursement document with the disbursement requestcommand.
 28. The DM computer device in accordance with claim 24, whereinsaid processor is further programmed to automatically transmit thedisbursement notification message to the payee computer device by atleast one of email, text message, and push alert.
 29. The DM computerdevice in accordance with claim 24, wherein said DM computer device isin communication with a payment card network, and wherein said processoris further programmed to: request the disbursement funds from an issuingbank associated with the payor; transmit an authorization requestmessage to a receiving bank associated with the payee, the authorizationrequest message requesting verification of the payee bank account;receive an authorization response message from the receiving bank, theauthorization response message including one of an affirmation and adenial of the authorization request; transmit the authorization responsemessage to the issuing bank; and instruct, in response to theauthorization response message being the affirmation, the issuing bankto disburse funds to the payee bank account.
 30. The DM computer devicein accordance with claim 24, wherein the payor is an insurance providerand the payee is a policyholder of the insurance provider, saidprocessor is further programmed to: receive the disbursement requestcommand from the insurance provider, the disbursement request commandinstructing the disbursement notification message to be sent from saidDM computing device to the policyholder, the disbursement requestcommand including the payee verification data that includes an insuranceclaim identifier; receive the disbursement request message from thepayee including a candidate claim identifier; and verify the payee bymatching the candidate claim identifier received from the payee to theinsurance claim identifier included in the disbursement request command.31. A computer-implemented method for processing an electronicdisbursement by a disbursement module (DM) computer device, wherein theDM computer device includes a memory device and a processor, said methodcomprising: registering a payor with a disbursement service provided bythe DM computer device using payor registration data received from apayor computer device associated with the payor; receiving adisbursement request command from the payor computer device, wherein thedisbursement request command instructs a disbursement notificationmessage to be sent from the DM computer device to a payee, thedisbursement request command including payee contact information, payeeverification data, and a disbursement amount to be paid to the payee,and wherein the payee verification data includes a payee identifier;generating the disbursement notification message including the payeeidentifier and a payor link, wherein the payor link is configured todirect the payee to a payor website in response to selection of thepayor link by the payee; automatically transmitting the disbursementnotification message to a payee computer device associated with thepayee; registering, via an electronic wallet application associated withsaid DM computer device, the payee in response to selection by the payeeof an electronic wallet application link displayed on the payor website,by receiving, from the payee computer device, an identification of atleast one bank account associated with the payee for receiving thedisbursement; receiving a disbursement request message from the payeerequesting that the disbursement be made to the payee, the disbursementrequest message including a candidate payee identifier; verifying thepayee by matching the candidate payee identifier to the payee identifierreceived with the payee verification data; and electronicallytransferring, in response to the registration and the verification,funds from a bank account associated with the payor to the bank accountassociated with the payee.
 32. The computer-implemented method inaccordance with claim 31, wherein the disbursement request command isone of a plurality of disbursement request commands, said method furthercomprising: receiving a batch file including the plurality ofdisbursement request commands, each of the disbursement request commandsidentifying one of a corresponding plurality of payees; and generatingthe disbursement notification message as one of a plurality ofdisbursement notification messages, each of the disbursementnotification messages corresponding to one of the plurality of payees.33. The computer-implemented method in accordance with claim 32, furthercomprising: identifying respective payee contact information and payeeverification data of the plurality of payees from within the batch file;and generating the disbursement notification messages each including thecorresponding payee identifier and a corresponding payor link.
 34. Thecomputer-implemented method in accordance with claim 31, furthercomprising: providing a disbursement document for display on the payorcomputer device; prompting the payor to input data into the disbursementdocument; and receiving the data input into the disbursement documentwith the disbursement request command.
 35. The computer-implementedmethod in accordance with claim 31, wherein automatically transmittingthe disbursement notification message to the payee computer device isaccomplished by at least one of email, text message, and push alert. 36.The computer-implemented method in accordance with claim 31, wherein theDM computer device is in communication with a payment card network, saidmethod further comprising: requesting the disbursement funds from anissuing bank associated with the payor; transmitting an authorizationrequest message to a receiving bank associated with the payee, theauthorization request message requesting verification of the payee bankaccount; receiving an authorization response message from the receivingbank, the authorization response message including one of an affirmationand a denial of the authorization request; transmitting theauthorization response message to the issuing bank; and instructing, inresponse to the authorization response message being the affirmation,the issuing bank to disburse funds to the payee bank account.
 37. Thecomputer-implemented method in accordance with claim 31, wherein thepayor is an insurance provider and the payee is a policyholder of theinsurance provider, further comprising: receiving the disbursementrequest command from the insurance provider, the disbursement requestcommand instructing the disbursement notification message to be sentfrom the DM computing device to the policyholder, the disbursementrequest command including the payee verification data that includes aninsurance claim identifier; receiving the disbursement request messagefrom the payee including a candidate claim identifier; and verifying thepayee by matching the candidate claim identifier received from the payeeto the insurance claim identifier included in the disbursement requestcommand.
 38. One or more non-transitory computer-readable storage mediahaving computer-executable instructions embodied thereon for processingan electronic disbursement by a disbursement module (DM) computerdevice, wherein the DM computer device includes a memory device and aprocessor, wherein when executed by said processor, saidcomputer-executable instructions cause the processor to: register apayor with a disbursement service provided by the DM computer deviceusing payor registration data received from a payor computer deviceassociated with the payor; receive a disbursement request command fromthe payor computer device, wherein the disbursement request commandinstructs a disbursement notification message to be sent from the DMcomputer device to a payee, the disbursement request command includingpayee contact information, payee verification data, and a disbursementamount to be paid to the payee, and wherein the payee verification dataincludes a payee identifier; generate the disbursement notificationmessage including the payee identifier and a payor link, wherein thepayor link is configured to direct the payee to a payor website inresponse to selection of the payor link by the payee; automaticallytransmit the disbursement notification message to a payee computerdevice associated with the payee; register, via an electronic walletapplication associated with said DM computer device, the payee inresponse to selection by the payee of an electronic wallet applicationlink displayed on the payor website, by receiving, from the payeecomputer device, an identification of at least one bank accountassociated with the payee for receiving the disbursement; receive adisbursement request message from the payee requesting that thedisbursement be made to the payee, the disbursement request messageincluding a candidate payee identifier; verify the payee by matching thecandidate payee identifier to the payee identifier received with thepayee verification data; and electronically transfer, in response to theregistration and the verification, funds from a bank account associatedwith the payor to the bank account associated with the payee.
 39. Theone or more non-transitory computer-readable storage media in accordancewith claim 38, wherein the disbursement request command is one of aplurality of disbursement request commands, and wherein saidcomputer-executable instructions further cause said processor to:receive a batch file including the plurality of disbursement requestcommands, each of the disbursement request commands identifying one of acorresponding plurality of payees; and generate the disbursementnotification message as one of a plurality of disbursement notificationmessages, each of the disbursement notification messages correspondingto one of the plurality of payees.
 40. The one or more non-transitorycomputer-readable storage media in accordance with claim 38, whereinsaid computer-executable instructions further cause said processor to:provide a disbursement document for display on the payor computerdevice; prompt the payor to input data into the disbursement document;and receive the data input into the disbursement document with thedisbursement request command.
 41. The one or more non-transitorycomputer-readable storage media in accordance with claim 38, whereinsaid computer-executable instructions further cause said processor toautomatically transmit the disbursement notification message to thepayee computer device by at least one of email, text message, and pushalert.
 42. The one or more non-transitory computer-readable storagemedia in accordance with claim 38, wherein the DM computer device is incommunication with a payment card network, and wherein saidcomputer-executable instructions further cause said processor to:request the disbursement funds from an issuing bank associated with thepayor; transmit an authorization request message to a receiving bankassociated with the payee, the authorization request message requestingverification of the payee bank account; receive an authorizationresponse message from the receiving bank, the authorization responsemessage including one of an affirmation and a denial of theauthorization request; transmit the authorization response message tothe issuing bank; and instruct, in response to the authorizationresponse message being the affirmation, the issuing bank to disbursefunds to the payee bank account.
 43. The one or more non-transitorycomputer-readable storage media in accordance with claim 38, wherein thepayor is an insurance provider and the payee is a policyholder of theinsurance provider, and wherein said computer-executable instructionsfurther cause said processor to: receive the disbursement requestcommand from the insurance provider, the disbursement request commandinstructing the disbursement notification message to be sent from the DMcomputing device to the policyholder, the disbursement request commandincluding the payee verification data that includes an insurance claimidentifier; receive the disbursement request message from the payeeincluding a candidate claim identifier; and verify the payee by matchingthe candidate claim identifier received from the payee to the insuranceclaim identifier included in the disbursement request command.